Repository navigation
v0.3.3: replace first() with 1-based index access - #6
Merged
Merged
Conversation
first(ifempty(path, emptyarray)) still threw IMLError on a 401 or HTML body in a live Make run. emptyarray is a scenario-mapper constant and is not defined in custom-app IML, so first() still received undefined. List-item outputs now use path[1], which returns empty on a missing path instead of throwing. response.valid still marks a missing API object as InvalidAccessTokenError. The offline IML helper treats indexes as 1-based.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Follow-up to #5. Live B1 still failed with
IMLError: Function 'first' finished with error! Invalid array.afterfirst(ifempty(path, emptyarray))was uploaded, becauseemptyarrayis a scenario-mapper constant and is not defined in custom-app IML.List-item outputs (Get Property Details, Verify Address, and the billed instant trigger's property lookup) now use IML 1-based index access (
path[1]), which returns empty on a missing path instead of throwing.response.validstill marks a missing API object asInvalidAccessTokenError. The offline IML test helper now treats numeric indexes as 1-based.npm test is 80/80.